Hello together, we have issues with Backup of exchange related AD objects. Our Backup tool (EMC Networker) throws this error message: * DC_SERVER_NAME:DC=de,DC=a***,DC=local LDAP://localhost/CN=StoreEvents{96C59C43-2E41-40E3-8FCA-3F2C92D908B2},CN=Microsoft Exchange System Objects,DC=de,DC=a***,DC=local , Error:Object reference not set to an instance of an object. We are currently running Exchange2010. Before it was 2007 and before that it was Exchange 2003. We noticed this error since Exchnage 2010 installation. The strange thing is: We have in "Microsoft Exchange System Objects" 10 of the StoreEvent{GUID} ofbjects. 3 of them can be backed up and 7 not. We have compared them via ADSI to find a difference but could not find anything. These objects have something to do with 2003 Public folders. Because there is something with FIRST ADMINISTRATIVE GROUP. An the creation date is is also in the very past 2005. Do you know what the error message means? Can we just delete the objects? Any ideas? Thanks in advance

On Fri, 4 Mar 2011 14:00:36 +0000, HaPe75 wrote: >we have issues with Backup of exchange related AD objects. Our Backup tool (EMC Networker) throws this error message: > >* DC_SERVER_NAME:DC=de,DC=a***,DC=local LDAP://localhost/CN=StoreEvents{96C59C43-2E41-40E3-8FCA-3F2C92D908B2},CN=Microsoft Exchange System Objects,DC=de,DC=a***,DC=local , Error:Object reference not set to an instance of an object. > >We are currently running Exchange2010. Before it was 2007 and before that it was Exchange 2003. We noticed this error since Exchnage 2010 installation. > >The strange thing is: > >We have in "Microsoft Exchange System Objects" 10 of the StoreEvent{GUID} ofbjects. 3 of them can be backed up and 7 not. We have compared them via ADSI to find a difference but could not find anything. These objects have something to do with 2003 Public folders. Because there is something with FIRST ADMINISTRATIVE GROUP. An the creation date is is also in the very past 2005. > >Do you know what the error message means? Can we just delete the objects? Any ideas? The value between the "{" and "}" is the objectGUID value of the database. For the StoreEvents objects that don't match the GUID of any database, you can remove it from the AD. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hey Rich, thanks for reply. How can I find out that the GUIDs do not match to the Database? Is it the CMDLET "get-publicfolderdatabase | FL" Or is there an other way to figure out which object can be removed. I want just to be sure before removing anything :o) Thanks HaPe

On Mon, 7 Mar 2011 08:54:32 +0000, HaPe75 wrote: >thanks for reply. How can I find out that the GUIDs do not match to the Database? > >Is it the CMDLET "get-publicfolderdatabase | FL" This will get you a list of all the mailbox database guids: Get-MailboxDatabase | ft server,storagegroup,name,guid -auto >Or is there an other way to figure out which object can be removed. The system mailbox AD object isn't a user, so you'd have to use .Net object to search the AD for them. If you don't have that many of them it shouldn't take long to matche the mailbox database guids to the system mailbox objects and exclude the ones that have no matches. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Rich, thanks for your help. Store Events are all gone now. Our Backup is claiming now about Objects Called "schema-root" Like this: DC_SERVERNAME:DC=de,DC=a***,DC=local LDAP://localhost/CN=schema-root 69282333,CN=Microsoft Exchange System Objects,DC=de,DC=a***,DC=local , Error:Object reference not set to an instance of an object. I checked via ADSIEDIT and could find that these object are also from 2003. Do you know If I can remove them as well? Thanks in Advance. HaPe

On Fri, 11 Mar 2011 09:39:41 +0000, HaPe75 wrote: > > >Hi Rich, > >thanks for your help. Store Events are all gone now. > >Our Backup is claiming now about Objects Called "schema-root" > >Like this: > >DC_SERVERNAME:DC=de,DC=a***,DC=local LDAP://localhost/CN=schema-root 69282333,CN=Microsoft Exchange System Objects,DC=de,DC=a***,DC=local , Error:Object reference not set to an instance of an object. > >I checked via ADSIEDIT and could find that these object are also from 2003. Do you know If I can remove them as well? You need one schema-root object. Using LDP.exe is probably easier than ADSIEDIT to look at multiple properties of AD objects, so I'd use that and see what's different between the "schema-root" and "schema-root 69282333". Neither one should actually have a replica in a public folder store since the schema-root is just a container. The structure should look like this when viewed from the E2K3 ESM: schema-root <== container ...Default ...microsoft <== container .....exchangeV1 If you see "schema-root XXXX" and its Default and exchangeV1 folders have no replicas you should be able to remove that "schema-root XXXX" and its sub-folders. A better alternative is to stop making those brick-level backups. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP